DNS on NT4 1

[larshald]

Hello !

I am facing a challenge, and i hope that someone here can help mee.

I need to configure a DNS server for a company to resolve internal DNS requests. The server is a NT4. I would like the domain name to be the same as the name registered on the internet.

I is not possible for me to make a secondary zone for the domain, because i need to add entries for internal hosts, if I configure the server as secondary, these entries would be overwritten.

If i configure the server as primary for the zone, will it collide with the DNS from my ISP ?

Does the DNS server in NT4 support domain names ending on .local, like W2K DNS server does ? This could also solve my problem, but simply upgrading to W2K server is not an option.

Thanks

\Lars

---
Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little more effort.
---

 

[Ntr0P]

You can make your TLD whatever you like in NT4. Thus if you want abc.local - go for it.

Creating the same domain name in NT as you have on the Internet is not an issue if yours is a primary as well.

 

[larshald]

Hmm...

In my mind there can only be one primary DNS server for anny given domain (the authoritative server). Are you sure that it will not collide with the ISP.

the .local domain is used in W2K as a "nonroutet" domain, but does NT4 understand this. I guess someone would be rather mad at me if i claimed to be authoritative for the .local domain.

\Lars

---
Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little more effort.
---

 

[Ntr0P]

No one would ever get to your DNS server with a .local TLD (except those who use it for their primary/secondary DNS). If your DNS server is public, .local will not be usable by anyone outside your organization. If someone keys an address such as abc.local, their DNS server will send the query off to one of the TLD DNS servers which will in turn have no clue what .local is.

Why would your primary DNS server overwrite the actual primary? They aren't aware of one another. Any secondaries should be pointing the real primary - so again not an issue. Since you would be the Authoritative server, the buck would stop with you for anyone querying your server. If someone queries your domain on your server, your server is not going to look elsewhere for an answer.

I inherited the same set up here and it works fine. I just need to make sure if their is an IP address change on the real primary that I change it on our DNS server as well.

 

[larshald]

What you are saying is:

I can configure the NT4 DNS with abc.com as a primary DNS even when my ISP has the authoritative DNS for abc.com.

My NT4 server is connectet to the internet, but behind a NAT and a firewall.

Will the event viewer not log an error simular to "the server "servername" think it is authoritative for the domain abc.com, but it is not" ?

If the above statements are correct..... ;-) !!

\Lars ---
Why make things difficult, when it is possible to make them cryptic and totally illogic, with just a little more effort.
---

 

[Ntr0P]

Yes, you can configure your NT4 DNS as primary without a problem.

You say your NT4 server is connected to the Internet, that is fine so long as it is not acting as an Internet DNS server. If you are just the DNS server for your org, you won't have an issue.

You won't have errors in the event log. Since you are claiming to be Authoritative, as mentioned before, if a user in your org queries your DNS server for a host in that domain, the DNS server will not query recursively since it is Authoritative. Hopefully that makes sense.