DNS setting quesiton. nslookup returns two IPs (one 192.168.x.x, the other 24.105.x.x)

  • Thread starter Thread starter xman
  • Start date Start date
X

xman

I have the W2K3 DNS server setup recently.

The DNS server is on our DC with only one internal IP address
(192.168.x.x). It works for our internal network (both internal name
and outside internet address)

We have both website and email server in the internal network, now I
want this DNS server to reply the outsider's DNS request. So I add an
A record for our domain name "mycompanyname.com" as "24.105.x.x", and
setup my firewall to forward port 53 to the local IP.

Now when I use the following command from my home (different ISP):

dig @24.105.x.x mycompanyname.com

it returns:

;; ANSWER SECTION:
mycompanyname.com. 600 IN A 192.168.x.x
mycompanyname.com. 600 IN A 24.105.x.x

I delete the record of "(same as parent)" for 192.168.x.x, it will
work for a while (just one IP return), but after a while the local IP
address record comes back again.

How can I fix this problem?

- Josh
 
In
xman said:
I have the W2K3 DNS server setup recently.

The DNS server is on our DC with only one internal IP address
(192.168.x.x). It works for our internal network (both internal name
and outside internet address)

We have both website and email server in the internal network, now I
want this DNS server to reply the outsider's DNS request. So I add an
A record for our domain name "mycompanyname.com" as "24.105.x.x", and
setup my firewall to forward port 53 to the local IP.

Now when I use the following command from my home (different ISP):

dig @24.105.x.x mycompanyname.com

it returns:

;; ANSWER SECTION:
mycompanyname.com. 600 IN A 192.168.x.x
mycompanyname.com. 600 IN A 24.105.x.x

I delete the record of "(same as parent)" for 192.168.x.x, it will
work for a while (just one IP return), but after a while the local IP
address record comes back again.

How can I fix this problem?

- Josh
Click to expand...

This is just one of the many problems with trying to host a public and
private DNS zone for the same name on the same DNS server. The issue is
compounded if the domain is also your AD domain name.
When the domain name of the AD domain is resolved for AD domain members it
must resolve to an IP address the has file sharing enabled. This is so the
DFS share that holds group policies can be found.
 
Back
Top