DNS on a domain
On our domain we have a PDC which also serves as the DNS for devices connected to the domain. We have an email server on a separate machine with a static IP address. For the users connected to the domain I would like calls to that machine (emailsvr) to use the domain IP address (192.x.x.x). For mobile users (i.e., laptops) I want the domain IP address used when connected to the domain and the public IP address used when outside the domain.
Currently all calls to the email server route through the public IP (been working that way for years) even if connected to the domain. Seems a roundabout way to get to a server that is on the domain.
I have tried LMHOSTS on the PDC and have the TCP/IP protocol selected to use LMHOSTS. In that file on the PDC I have an entry with "IP Adresss emailsvr #PRE" (w/o the quotes).
Any clues?
Currently all calls to the email server route through the public IP (been working that way for years) even if connected to the domain. Seems a roundabout way to get to a server that is on the domain.
I have tried LMHOSTS on the PDC and have the TCP/IP protocol selected to use LMHOSTS. In that file on the PDC I have an entry with "IP Adresss emailsvr #PRE" (w/o the quotes).
Any clues?
ASKER
We are not using Exchange.
The DC is set to be the DNS for the computers who are connected to the domain. Most of the computers are fixed workstations which never leave the office so it makes since for them to point directly to the 192.x.x.x IP address of the mail server. However, laptops need to use the public IP of the server when not connected to the domain. I would like the laptops to use the 192.x.x.x IP address when they are in the office connected to the domain. Seems more efficient.
I saw split DNS on some search results but didn't read about it because I wasn't sure it fit what I am asking.
The DC is set to be the DNS for the computers who are connected to the domain. Most of the computers are fixed workstations which never leave the office so it makes since for them to point directly to the 192.x.x.x IP address of the mail server. However, laptops need to use the public IP of the server when not connected to the domain. I would like the laptops to use the 192.x.x.x IP address when they are in the office connected to the domain. Seems more efficient.
I saw split DNS on some search results but didn't read about it because I wasn't sure it fit what I am asking.
When the laptops are NOT connected to the domain, they're surely using the DNS server at the onsite location (which is different everytime depending on where they are) ? It means you just have to set your public DNS records straight?
Let your ISP do it, or ask them for the config panel so you can do it yourself.
So, i.e. INSIDE domain, mail.domain.com = 192.x.x.x.x (your own DNS server handles this)
OUTSIDE the domain, mail.domain.com = public IP (your domain registrar handles this, they have to do it, or you have a plesk or cpanel or whatever config page to do it)
Let your ISP do it, or ask them for the config panel so you can do it yourself.
So, i.e. INSIDE domain, mail.domain.com = 192.x.x.x.x (your own DNS server handles this)
OUTSIDE the domain, mail.domain.com = public IP (your domain registrar handles this, they have to do it, or you have a plesk or cpanel or whatever config page to do it)
ASKER
@Kimputer
Paragraph 1 ... agreed; this is not an issue.
Paragraph 2 ... INSIDE the domain is what I am trying to accomplish. The DC is the DNS and I tried using a LMHOSTS file to "guide" the DC to know to look inside the domain for mail.domain.com but it still goes outside the domain to the public IP.
Paragraph 1 ... agreed; this is not an issue.
Paragraph 2 ... INSIDE the domain is what I am trying to accomplish. The DC is the DNS and I tried using a LMHOSTS file to "guide" the DC to know to look inside the domain for mail.domain.com but it still goes outside the domain to the public IP.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@Kimputer and @Justin F...
Both your solutions were very helpful. I did the nslookup first to check those replies. Everything was consistent with the DNS for the mail server looking outside of the DNS on the DC.
I then used the DNS management console to add the email server as an (A) record and then pinged the mail.domain.com name. Still had the public IP. :|
I then renamed the LMHOSTS file to LMHOSTS.OLD, ran nbtstat -R and nbtstat -c from the command prompt and the local IP is now delivered back.
The full test will be Monday when everyone return to the office.
Thank you both.
Both your solutions were very helpful. I did the nslookup first to check those replies. Everything was consistent with the DNS for the mail server looking outside of the DNS on the DC.
I then used the DNS management console to add the email server as an (A) record and then pinged the mail.domain.com name. Still had the public IP. :|
I then renamed the LMHOSTS file to LMHOSTS.OLD, ran nbtstat -R and nbtstat -c from the command prompt and the local IP is now delivered back.
The full test will be Monday when everyone return to the office.
Thank you both.
ASKER
A *final* report (I hope) on the discussion above...The changes implemented Saturday appear to be sticking and not causing any issues with the users as they have returned to work this week. And access from outside the office via the public IP also remains undisturbed.
Thank you again!
Thank you again!
Is your Domain Controller hosting your company's public DNS or are you using split DNS?