 |  |
I am behind a NAT server on my LAN, one client i test on is on the
Re: config problems
From: john
Date: Wednesday, June 13, 2001
Time: 7:52:40 pm
same subnet (the same router) as the DNS machine. One client I
test on is on another subnet. The subnets do not, at this time
talk to each other.
I am dealing with all this in the first place because DNSWIZ went
down earlier in the week I assume because of the flooding in Texas.
It sounds like from your report that not all of thier servers are
back up, I had not checked that.
ns1.shore.net does not have any records of any of the virtual
domains. DNSWIZ name servers and my name servers
(ns1-2.trouncemedia.com) should match with all the DNS for this
domain. I added the shore.net servers back in the Register.com NS
record to get our site and mail back up ASAP. I then jumped into
trying to learn QuickDNS since it was clear that we should have
more back-up for DNS.
Once I thought I had my DNS server set, I added it to the records
at Register.com.
Should I now remove the shore.net servers from the Register.com
record, since they do not, and cannot support all the DNS info I
need for this domain?
The reason I Ieft it was that I assumed that if one of the name
servers listed at Register.com did not have the record for the
virtual domain (the canonical name) that it would try the next one
on the list, and that it would check every record if it had to
before it said "domain not found".
I assume this is not the case? I learned in a previous post (thank
you) that requests for names in trounce do not necessarily go in
the order that they are listed in the Register.com NS records, that
it takes the fastest server to respond to the request.
If my NAT server is causing me problems in my LAN that is fine, my
concerns is a client could not log on to his extranet with the
name, I had to send him an IP.
Can someone explain how to use my QuickDNS to just request the data
form DNSWIZ so that all that info is backed up?
Then I can dive into improving my DNS skills with a less critical domain...
Thanks for the support, it is very much appreciated.
>>>If you have a name we can test, the members of this list (myself
>>>included) can offer more specific help.
>>
>>One address I am having trouble with is:
>>http://monetrics.trouncemedia.com
>>
>>I cannot get to it from a machine on the same LAN, I have tried
>>with my client LAN machine with both the IP of the DNS server, and
>>with only the ISP's DNS ip's in it's TCP/IP settings.
>>
>>I did just reach it from a dial-up account.?? I don't get it.
>
>The inconsistency is caused by the fact that the various servers to
>which the zone is delegated don't all have the same data.
>
>The delegation records look like this:
> trouncemedia.com. NS ns1.shore.net.
> trouncemedia.com. NS ns1.dnswiz.com.
> trouncemedia.com. NS ns2.dnswiz.com.
> trouncemedia.com. NS ns2.shore.net.
> trouncemedia.com. NS ns3.dnswiz.com.
> trouncemedia.com. NS ns1.trouncemedia.com.
> ns1.shore.net. A 192.233.85.129
> ns1.dnswiz.com. A 207.91.131.30
> ns2.dnswiz.com. A 207.91.131.31
> ns2.shore.net. A 192.233.145.5
> ns3.dnswiz.com. A 65.201.81.100
> ns1.trouncemedia.com. A 24.147.23.107
>
>But ns1.shore.net and ns2.shore.net don't have any record of
>monetrics.trouncemedia.com. Their servers have the following records:
> trouncemedia.com. SOA northshore.ecosoft.com.
> postmaster.northshore.ecosoft.com.
> [...]
> trouncemedia.com. NS ns1.shore.net.
> trouncemedia.com. NS ns2.shore.net.
> trouncemedia.com. NS ns3.shore.net.
> trouncemedia.com. NS ns4.shore.net.
> ns1.shore.net. A 192.233.85.129
> ns2.shore.net. A 192.233.145.5
> ns3.shore.net. A 192.233.145.6
> ns4.shore.net. A 192.233.85.21
>
>Furthermore, the dnswiz.com servers have a different set of data:
> trouncemedia.com. SOA ns1.dnswiz.com.
> hostmaster.dnswiz.com.
> [...]
> trouncemedia.com. NS ns1.dnswiz.com.
> trouncemedia.com. NS ns2.dnswiz.com.
> trouncemedia.com. NS ns3.dnswiz.com.
> trouncemedia.com. NS ns4.dnswiz.com.
> ns1.dnswiz.com. A 207.91.131.30
> ns2.dnswiz.com. A 207.91.131.31
> ns3.dnswiz.com. A 65.201.81.100
> ns4.dnswiz.com. A 65.201.81.101
>
>Note that, of these servers, only ns3 and ns4 actually respond. They
>do, however, have a record for monetrics.trouncemedia.com.
>
>Of course, your server has a third set of data:
> trouncemedia.com. SOA ns1.trouncemedia.com.
> john.trouncemedia.com.
> [...]
> trouncemedia.com. NS ns1.trouncemedia.com.
> trouncemedia.com. NS ns2.trouncemedia.com.
> ns1.trouncemedia.com. A 24.147.23.107
> ns2.trouncemedia.com. A 24.147.23.105
>
>Now, regarding the machine on your LAN, are you behind a NAT server?
>That's about the only explanation that comes to mind.
>____________________________________________________________________
>Chris Buxton Men & Mice
>cbuxton@menandmice.com We Make DNS Easy!
Messages In This Thread:
Return to Digital Point Solutions' Home Page