dns issues

  • Thread starter Thread starter art
  • Start date Start date
A

art

I have a client that has a 2000 server running AD. It was
originally setup when i started working here about 1 month
ago pointing to outside dns sersvers...206.13.29.12,
206.13.30.12...i set it up to point to itself, then
enabled forwarders in dns to the above mentioned servers.
Now is where the fun begins. The clients are xp and 98.
they all were 2000 with 3 xp machines the last tech here
couldnt figure out bandwith problems so he said 2k makes
too much traffic lets bump them to 98. Some of the 98 pc's
have the pc name as one name and the dns name as another,
and dns domain name as pacbel.net for some and nothing for
others. But the standard domain name in 98 where insert
the domain is DOMAIN. Any ways to my point. If I change
the settings on the client machines to point to the
internal dns server instead of the external which they are
pointing to now they can not get email. But the net still
works. The two xp machines drop off the network each
night. I have to leave them pointing to the external dns
servers or they can not get their emails. They have to
reboot every morning and things get refreshed and their
fine, come in next day and they can not print or browse
network drives. I've tried the whole ipconfig flush and
register . Any help would be greatly appreciated.
Thanks, Art
 
In
art said:
I have a client that has a 2000 server running AD. It was
originally setup when i started working here about 1 month
ago pointing to outside dns sersvers...206.13.29.12,
206.13.30.12...i set it up to point to itself, then
enabled forwarders in dns to the above mentioned servers.
Now is where the fun begins. The clients are xp and 98.
they all were 2000 with 3 xp machines the last tech here
couldnt figure out bandwith problems so he said 2k makes
too much traffic lets bump them to 98. Some of the 98 pc's
have the pc name as one name and the dns name as another,
and dns domain name as pacbel.net for some and nothing for
others. But the standard domain name in 98 where insert
the domain is DOMAIN. Any ways to my point. If I change
the settings on the client machines to point to the
internal dns server instead of the external which they are
pointing to now they can not get email. But the net still
works. The two xp machines drop off the network each
night. I have to leave them pointing to the external dns
servers or they can not get their emails. They have to
reboot every morning and things get refreshed and their
fine, come in next day and they can not print or browse
network drives. I've tried the whole ipconfig flush and
register . Any help would be greatly appreciated.
Thanks, Art
Click to expand...

If your internal domain is the same name as your public domain you will need
to add records to your internal domain Forward Lookup Zone for the names
missing i.e. mail then give that record the IP address needed to access this
server.
You can also use a delegation for the name, pointing that delegation to the
Authoritative DNS Servers for the public domain.

You should not use your ISP's DNS in *any* NIC on any machine, use only your
Local DNS address. If you want you can use your ISP's DNS as a forwarder in
your DNS server as per step 3 of this KB Article:300202 - HOW TO Configure
DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202&FR=1
 
Thanks Kevin. Their internal Domain name is
flavorproducers.com and their web address is
www.flavorproducers.com ....We are running imail here on a
server and we give them their email which is the same
domain @flavorproducers.com. I am just getting aquainted
with w2k server from an admin perspective. So what would
you say I should do...Oh and I dont know If this matters
but eventhough internal domain name is flavorproducers at
logon it says DOMAIN. Another wierd thing that boggles me
is here at our site our root server which is our only
logon servers fully qualified name is an example
hal2000.pacbell.net but the domain name is hq.currie.com.
Their site and our site have the same pacbell dns servers
that theu forward to. The site your helping me with is not
setup that way. I dont know If that could be aproblem or
not?
 
In Ace Fekay [MVP] <PleaseSubstituteMyActualFirstName&[email protected]>
posted their concerns
Then Kevin made his reply below:
In Crazy <kevin@don't_spam_me_you_idiot.net> posted their thoughts, then
I offered mine
<snip>

Crazy now?

:-)

Ace
Click to expand...

It's a joke haha! I'm having trouble posting to the Microsoft news server so
I'm having to use SBC's news server.
 
In
art said:
Thanks Kevin. Their internal Domain name is
flavorproducers.com and their web address is
www.flavorproducers.com ....We are running imail here on a
server and we give them their email which is the same
domain @flavorproducers.com. I am just getting aquainted
with w2k server from an admin perspective. So what would
you say I should do...Oh and I dont know If this matters
but eventhough internal domain name is flavorproducers at
logon it says DOMAIN. Another wierd thing that boggles me
is here at our site our root server which is our only
logon servers fully qualified name is an example
hal2000.pacbell.net but the domain name is hq.currie.com.
Their site and our site have the same pacbell dns servers
that theu forward to. The site your helping me with is not
setup that way. I dont know If that could be aproblem or
not?
Click to expand...

If you are refering to the domain shown in the logon dialog, it uses the
NetBIOS name of the domain, which really has nothing to do with its DNS name
except by coincidence. You can use a different NetBIOS domain name, which is
the one you must use with legacy clients such as NT4 and Win9x.

If there internal DNS Domain name is flavorproducers.com then in the
flavorproducers.com forward lookup zone you need to create a host named mail
pointing to the IP you need to access your mail server. If the mail server
is located outside an NAT device the record must point to the public
address, if it is located locally behind NAT device it must point to its
private address.

Here is another thing to keep in mind *ALL* machines belonging to a Win2k
domain must point only to the internal DNS server for the AD Domain
including the DC or machine DNS service is running on.
 
In Ace Fekay [MVP] <PleaseSubstituteMyActualFirstName&[email protected]>
posted their concerns
Then Kevin made his reply below:
I see what you mean. I've been having some issues too. Long
connection times too. Guess busy...

Ace
Click to expand...

It is probably has something to do with the Swen worm.
 
In Crazy <kevin@don't_spam_me_you_idiot.net> posted their thoughts, then I
offered mine
<snip>

Crazy now?

:-)

Ace
 
Back
Top