DNS Problem: Resolving ONLY the Domain

  • Thread starter Thread starter Andrew Wilcox
  • Start date Start date
MF> an Alias is a CNAME - canonical name that points to another name

Actually, it's the name that is "pointed" to that is "canonical". See RFC
2181 section 10.1.1. The whole notion of "canonical names" is a misleading
one. "Alias" is the more descriptive, and better, term. A "CNAME" resource
record is a client-side alias.
 
In
Andrew Wilcox said:
As I said before..."the HOST record thedomain1.com could not be
created." The NODE is a CNAME DNS record.

How can a node by an alias? I am using AD-Integrated...is that bad?
Click to expand...

Is there a blank CNAME record in the zone already?
You can have multiple hosts in a zone with the same name, but you can only
have one CNAME record per name.
Delete the Alias record.
 
I scrolled the boxes down so you can see my entire DNS setup...it's only 24k
because I used ZIP.

I use dial-up, if you need me to post a real BMP, let me know.

Andrew Wilcox
Andre\/\/\/are

"Ace Fekay [MVP]"
 
In
Andrew Wilcox said:
I scrolled the boxes down so you can see my entire DNS setup...it's
only 24k because I used ZIP.

I use dial-up, if you need me to post a real BMP, let me know.

Andrew Wilcox
Andre\/\/\/are
Click to expand...

Hi Andrew,

Did you attach the zip file?


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
The original problem was that you can't have a CNAME
record attached to an interior node, like in your case
theDomian.com, when it owns other records. This' why the
CNAME did not work (in BIND the zone won't load).

Then when you try to add the A record to the domain,
because there is already the CNAMe record, it violates
the rule that a domain name be either an alias or a
canonical name, not both.

Your solution, remove the CNAME record (domain.com ->
server.domain.com)first, create the A record for the
theDomian.com, and you can keep the
theServer.theDomain.com. A record.

-----Original Message-----
Hello All,

I have a Windows 2000 Primary Domain Controller (name:
theNEW4850.theDOMAIN1.com) with DNS installed. When I type in just the
domain name (theDOMAIN1.com) into my web browser, my Exchange IM Client,
Outlook, or anything else for that matter, it comes back a DNS error. If I
type in the name including the computer (theNEW4850 or
theNEW4850.theDOMAIN1.com), everything comes up. The problem is mainly that
the IM Client says that
Click to expand...
(e-mail address removed)1.com doesn't
 
In
Andrew Wilcox said:
Did it, tried it, no luck. I ran ipconfig /registerdns and it still
doesn't work. I've 2 screens in this attach (yes, I 'membered):
Click to expand...

From what I see if you do a lookup against this DNS server for
theDOMAIN1.com it should resolve to 192.168.0.2.
Are you sure you are using the correct DNS address. From what I see this
server's IP address is 192.168.0.2 but you have 192.168.0.1 in the NIC. Does
the server at 192.168.0.1 have this zone in it?

run ipconfig /flushdns
Does the site this is pointing to have a host header?

It may not be related to the problem but is this domain an Active Directory
domain?
If it is I don't see the AD sub folders.
 
looks like you are using a routor as the dns and gateway
for internet resolution...

you are not using your dns at all.

you may reconfigure you machine to use your dns (the
machine itself) as the dns and set up the router as a
forwarder for the dns server.
 
192.168.0.1 is the IP of my DHCP server, running 98SE. Can it even run DNS?
If so, please tell me how to install.

No host headers.

Where are the folders supposed to be?

No, I don't have a router, I have a switch?

Andrew Wilcox
Andre\/\/\/are
 
ok just suprises...

how about you chnage your dns to 192.168.0.2? (why you
use 192.168.0.1 in the first place?)

or use a hosts file to get this thing over?
 
In
Andrew Wilcox said:
192.168.0.1 is the IP of my DHCP server, running 98SE. Can it even
run DNS? If so, please tell me how to install.
Click to expand...

You are using ICS on WIn98? ICS has a DNS proxy in it to your ISP's DNS.
You are not even using the correct DNS address, manually configure
192.168.0.2 into this box for DNS.
Then configure this DNS server with a forwarder to your ISP's DNS. For you
to access the sites on this server you need to use its address for DNS on
all your internal machines.
It is very important that you configure your DC to use its own address for
DNS.
Where are the folders supposed to be?
Click to expand...

They are supposed to be in your AD forward lookup zone, they are:
_msdcs
_udp
_tcp
_sites

Once you point this DC to its own address for DNS, restart the netlogon
service and run netdiag /fix that should create the sub folders and SRV
records.
Right now the DC probably take fifteen minutes to start and is logging 5774
events, right?
 
Now that I set the DNS, I get nowhere in IE (but obviously I can use the
'Net).

Here is my inline post:
You are using ICS on WIn98? Yes.
ICS has a DNS proxy in it to your ISP's DNS.
You are not even using the correct DNS address, manually configure
192.168.0.2 into this box for DNS. Did it already.
Then configure this DNS server with a forwarder to your ISP's DNS.
Click to expand...
When I set up DNS on 3/19/04, I read the help file, printed the checklist,
and checked almost everything. Done.
For you to access the sites on this server you need to use its address for DNS on
all your internal machines.
Click to expand...
Including the ICS server? Won't that screw everyone up?
It is very important that you configure your DC to use its own address for
DNS. Did it.

They are supposed to be in your AD forward lookup zone, they are:
_msdcs
_udp
_tcp
_sites
Click to expand...
How do I set them up? I never did see any of those.
Once you point this DC to its own address for DNS, restart the netlogon
service and run netdiag /fix that should create the sub folders and SRV
records.
Click to expand...
Where do I find netdiag? "'netdiag' is not a recognized as a internal or
external c..."
Right now the DC probably take fifteen minutes to start and is logging 5774
events, right?
Click to expand...
Well, the 5774 errors stopped on 3/24/04. And on 3/21 it took almost 40
minutes to get to the 'Configure Your Server' screen.
 
In
Including the ICS server?
Click to expand...
Yes, if you want to access sites on the server from it.

Won't that screw everyone up?
No.
Your internal DNS server will resolve everything.

How do I set them up? I never did see any of those.
Click to expand...

The DC will create these records.

Where do I find netdiag? "'netdiag' is not a recognized as a
internal or external c..."
Click to expand...

netdiag is a part of the server support tools on the server CD this will
also install dcdiag, another important diagnostic tool for Active Directory
domains.
 
I can't resolve outside servers through here? What'd I do wrong?

Andrew Wilcox
Andre\/\/\/are
 
so your w98 is acting as your router..change everything
back to the original on w98. don't add your dns there..

on your dns use the w98 as a forwarder.

on you machine (i.e. the dns machine), use itself as the
dns (reconfigure your nic ip/tcp properties, replacing
the w98).

this way, all local names will be resolved locally, using
your dns (including theDomain.com; remove the "." if you
have one, otherwise you cannot set up the forwarder); all
the internet names will be forwarded by your dns to your
isp dns for resolution.
 
In
the confused said:
so your w98 is acting as your router..change everything
back to the original on w98. don't add your dns there..

on your dns use the w98 as a forwarder.
Click to expand...

If he does that he won't be able to resolve the local names from the Win98
box.
 
In
Andrew Wilcox said:
209.152.0.5
209.152.16.20
(both by my ISP)
Click to expand...

Maybe they have these blocked but I can get these to resolve anything. Try
these as forwarders 4.2.2.1 and 4.2.2.2.

This DNS server actually should not really need a forwarder to resolve
external names, it should be able to use its root hints.
If you need to resolve the sites on this server locally you must use it for
DNS.
 
Back
Top