Windows NT4 DNS Server question

[DS]

Hello,

We have one old Windows NT4.

We want to use it only to work as DNS server, to provide DNS services for
external remote VPN hosts that are not in our Windows 2003 Domain.
We want to mantain only one primary zone in that server with our intranet
resource records.

Question:
In the xpto.org zone we have one record called "intranet" to 172.16.30.25.
This way, users can acces our intranet server by the URL "intranet.xpto.org".
However we want that, if users only write the URL "xpto.org", can also
access our intranet server.
So, users can write "intranet.xpto.org" ou "xpto.org" to access our intranet
server (172.16.30.25).

This can be done with windows 2000/2003 server. But how to do it with
Windows Server NT4?

I already tried to modify the dns zone file, but without success.

Thanks and Best Regards
Duarte S.

 

[Herb Martin]

Hello,

We have one old Windows NT4.

We want to use it only to work as DNS server, to provide DNS services for
external remote VPN hosts that are not in our Windows 2003 Domain.
We want to mantain only one primary zone in that server with our intranet
resource records.

It must be at least SP4 but since ALL NT4 computers should have
SP6A + Hotfixes this should not be an issue.

SP4 is required to support the DNS SRV records as a domain zone
secondary.

Question:
In the xpto.org zone we have one record called "intranet" to 172.16.30.25.

This way, users can acces our intranet server by the URL
"intranet.xpto.org".

However we want that, if users only write the URL "xpto.org", can also
access our intranet server.

So, users can write "intranet.xpto.org" ou "xpto.org" to access our
intranet
server (172.16.30.25).

This can be done with windows 2000/2003 server. But how to do it with
Windows Server NT4?

No it cannot easily be done with an AD Domain, independent of
NT4/2003 DNS.

The reason is that all of your DCs register the 'bare' DOMAIN NAME
by default.

I already tried to modify the dns zone file, but without success.

You cannot modify a 'secondary' as it updates from its master.

 

[DS]

Hello,

Thanks for you answer.

We don't want to integrate AD with Windows NT4 DNS server!.

I only want to publish to our branch hosts (and they not belong to our AD
domain) a resource record for a machine that is in our internal network.

It's a simple thing to do. We already did it and works.

The problem is we want that hosts access that machine by the FQDN
(intranet.xpto.org) or only by the domain name (xpto.org).
We only need to point intranet.xpto.org and xpto.org to the same IP address.

Like the same we do to access Microsoft. We can write in the browser
"www.microsoft.com" or only "microsoft.com".

With Windows NT4 DNS server is simple to add the resource record
"intranet.xpto.org" pointing to one IP address. Now, how can we do this if we
want access the same IP address only by the domain name "xpto.org"?

 

[Herb Martin]

Hello,

Thanks for you answer.

We don't want to integrate AD with Windows NT4 DNS server!.
I only want to publish to our branch hosts (and they not belong to our AD
domain) a resource record for a machine that is in our internal network.
It's a simple thing to do. We already did it and works.

Then NT4 there is not an issue and can be left out of your
consideration (and question.)

The problem is we want that hosts access that machine by the FQDN
(intranet.xpto.org) or only by the domain name (xpto.org).

That's fine OUTSIDE, but not INSIDE.

We only need to point intranet.xpto.org and xpto.org to the same IP
address.

You can use a second A record (for intranet) or you can use
a CNAME to map one to the other.

Like the same we do to access Microsoft. We can write in the browser
"www.microsoft.com" or only "microsoft.com".

Add an "empty" or "same as parent" record with the domain name.

With Windows NT4 DNS server is simple to add the resource record
"intranet.xpto.org" pointing to one IP address. Now, how can we do this if
we
want access the same IP address only by the domain name "xpto.org"?

CNAME works.

A record works.

 

[DS]

Hello again and Thanks again,

You said: "Add an "empty" or "same as parent" record with the domain name."

From what I know and tried, I cand do this with Windows 2000/2003 DNS
Server, but not with Windows NT4 Server....and this is the exact problem....

Best regards
Duarte S.

 

[Herb Martin]

Hello again and Thanks again,

You said: "Add an "empty" or "same as parent" record with the domain
name."

From what I know and tried, I cand do this with Windows 2000/2003 DNS
Server, but not with Windows NT4 Server....and this is the exact
problem....

I don't remember that being a problem with WinNT, and would
swear that this can be done.

I have a vague idea that there might be some additional "gui" trick
to make it work, or the wording is different from what is used in
Windows Server now.

Try this Google search:

[ site:microsoft.com NT 4.0 | 4 dns server "same as parent" | blank |
empty "A record" ]

Probably a good idea to go ahead and upgrade NT4 also.

 

[Ace Fekay [MVP]]

In

Hello again and Thanks again,

You said: "Add an "empty" or "same as parent" record with the domain
name."

From what I know and tried, I cand do this with Windows 2000/2003
DNS Server, but not with Windows NT4 Server....and this is the exact
problem....

I don't remember that being a problem with WinNT, and would
swear that this can be done.

I have a vague idea that there might be some additional "gui" trick
to make it work, or the wording is different from what is used in
Windows Server now.

Try this Google search:

[ site:microsoft.com NT 4.0 | 4 dns server "same as parent" | blank
| empty "A record" ]

Probably a good idea to go ahead and upgrade NT4 also.

It's been some time, but I remember to create a blank domain A record under
NT4, you have to go into the actual DNS zone text file (winnt\system32\dns)
to create it. If I remember correctly, the record in the zone file would
look like:

@ A x.x.x.x

Then bump up the serial number by 1 digit.

Then refresh the NT4 DNS console from the zone file.

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Infinite Diversities in Infinite Combinations

 

[Herb Martin]

In

Hello again and Thanks again,

You said: "Add an "empty" or "same as parent" record with the domain
name."

From what I know and tried, I cand do this with Windows 2000/2003
DNS Server, but not with Windows NT4 Server....and this is the exact
problem....

I don't remember that being a problem with WinNT, and would
swear that this can be done.

I have a vague idea that there might be some additional "gui" trick
to make it work, or the wording is different from what is used in
Windows Server now.

Try this Google search:

[ site:microsoft.com NT 4.0 | 4 dns server "same as parent" | blank
| empty "A record" ]

Probably a good idea to go ahead and upgrade NT4 also.

It's been some time, but I remember to create a blank domain A record
under NT4, you have to go into the actual DNS zone text file
(winnt\system32\dns) to create it. If I remember correctly, the record in
the zone file would look like:

@ A x.x.x.x

Then bump up the serial number by 1 digit.

Then refresh the NT4 DNS console from the zone file.

Thanks Ace, that sounds right -- I almost added that but couldn't
remember all the details about setting NT4 to use Files vs.
Registry etc.

 

[Ace Fekay [MVP]]

In

Thanks Ace, that sounds right -- I almost added that but couldn't
remember all the details about setting NT4 to use Files vs.
Registry etc.

My pleasure. I had to dig back through memory for that one! With NT4 I
believe it was all files. If I remember, the reg just referenced the
service.

Ace

 

[Bob In the Noc]

While I'm no fan of a hosts file, this might be a good candidate if it means
taking an NT4 server offline, especially if it's only purpose is to server 1
zone with only 2 records.... Which is worse, manually working the hosts
files on each PC (maybe send as email attachment with good info on how to
place it) or praying that the Nt4 box continues to run unimpeded?

 

[Ace Fekay [MVP]]

In

While I'm no fan of a hosts file, this might be a good candidate if
it means taking an NT4 server offline, especially if it's only
purpose is to server 1 zone with only 2 records.... Which is worse,
manually working the hosts files on each PC (maybe send as email
attachment with good info on how to place it) or praying that the Nt4
box continues to run unimpeded?

I didn'y say anything about the hosts file. I was talking about the actual
DNS zone file that can be found in \system32\dns folder with the name of,
using domain.com as an example, in the domain.com.dns file.

Ace