Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Strange DNS Behaviour

Status
Not open for further replies.

ninpeh

MIS
Feb 28, 2002
3
SG
Hi guys,

I am running a windows 2003 server. The machine serves as a mail server, domain name server and web server.

I've configured the machine to host 2 IP addresses on one NIC, with Primary website pointing to 192.1.1.1 and Secondary website to 192.1.1.2

As such, the DNS automatically created 2 Host (A) records. I removed the record containing 192.1.1.2 so that my user can access the Primary website with and Secondary website with
However, the record I deleted always seem to come back itself, thus users who surf to will ends up viewing the Secondary website instead.

I went to Forward Lookup Zones->Properties->Name server and realised that the FQDN has got 2 IP address: [192.1.1.2][192.1.1.1]

I remove 192.1.1.2 from the name server but after a while, it comes back.
I tried changing the sequence but the FQDN will still shows [192.1.1.2][192.1.1.1] instead of [192.1.1.1][192.1.1.2]

Can someone tell me what should I do to prevent DNS from creating this Host record automatically? Or how can I make DNS return 192.1.1.1 as the default IP instead of 192.1.1.2?
 
hi,

Below is list what I have to do when I create VPN (gateway to gateway) and the vpn server is DNS Server also. Maybe this apply to you?

Server registers its virtual IP Address to DNS Add value in Registry: DisableDynamicUpdate (REG_DWORD Value: 1 )--
>HKLM SYSTEM CurrentControlSet Tcpip Parameters

Server registers its virtual IP Address to DNS Add value in Registry: PublishAddresses (REG_SZ Value: 192.1.1.1) -->HKLM SYSTEM CurrentControlSet Services DNS Parameters

Prevent Netlogon service from automaticallly registering entries in the netlogon.dns Add value in Registry: UseDynamicDns (REG_DWORD Value: 0 ) --> HKLM SYSTEM CurrentControlSet Services Netlogon Parameters

Prevent Netlogon service from automaticallly registering entries in the netlogon.dns Add value in Registry: RegisterDNSARecords (REG_DWORD Value: 0 ) --> HKLM SYSTEM CurrentControlSet Services Netlogon Parameters
 
this is because the NIC is set to register in DNS automatically...which it needs to be for a DC...it is not recommended to have more than 1 IP on a DC (especially not multihomed)...but in your configuration, it is accaptable because we are talking two IPs on one NIC, and those IPs are in the same subnet...to answer your question...it will not be possible to not have that IP register in DNS along with 192.168.1.1....I believe the foreground DNS record refresh is every 1.5 hrs or so...so if you were to reboot the machine is question, delete the record from DNS for 1.2...about 1.5 hrs later you should see it return....again, this is by design...and NO, a second NIC is not the solution here. In your case, I would say to set the web site to use 1 IP or the other, and not allow access through both IPs...either that, or mimic the web content so there is another page to respond to .1.2

-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there :)
 
thanks. already found the solution to that.
in DNS, i choose to listen to specify IP Address instead of all IP addresses.
 
perfect...I actually meant ot put that into my note up there as well

glad to hear you got it solved though :)

-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top