resolv2 content

[Fred Blau]

My \mptn\etc\resolv2 file contain 3 lines:

domain <name of domain>
nameserver <IP address of 1st DNS>
nameserver <IP address of 2nd DNS>

where <name of domain> matches that in \ibmlan\ibmlan.ini, and the
numerical IP addresses for the domain name servers are what my ISP
provided.

My LAN is a peer network. Today I deleted the first line of resolv2 and
rebooted, then connected to my LAN and saw nothing unusual. I also
connected to the Internet (the LAN has a router between the computers
and the DSL modem) without trouble.

Question: Is the domain line needed for anything?

[Fred Blau]

Question #2: I replaced the two nameserver lines with a single line:

nameserver <LAN IP address of my router>

and this seems to work just as well. The router, a Linksys WRT54G,
knows the IP addresses of the two DNSs. Is there any reason to prefer
this one DNS approach over the other?

Post by Fred Blau
domain <name of domain>
nameserver <IP address of 1st DNS>
nameserver <IP address of 2nd DNS>
where <name of domain> matches that in \ibmlan\ibmlan.ini, and the
numerical IP addresses for the domain name servers are what my ISP
provided.
My LAN is a peer network. Today I deleted the first line of resolv2 and
rebooted, then connected to my LAN and saw nothing unusual. I also
connected to the Internet (the LAN has a router between the computers
and the DSL modem) without trouble.

[Bob Eager]

Post by Fred Blau
nameserver <LAN IP address of my router>
and this seems to work just as well. The router, a Linksys WRT54G,
knows the IP addresses of the two DNSs. Is there any reason to prefer
this one DNS approach over the other?

Not really. I'd use whichever is least likely to change (e.g. if the
router gets its knowledge from DHCP, get yours from the router, since
you'll know if its address changes).

[Trevor Hemsley]

On Fri, 25 May 2007 14:39:08 UTC in comp.os.os2.networking.misc, "Fred Blau"

Post by Fred Blau
nameserver <LAN IP address of my router>
and this seems to work just as well. The router, a Linksys WRT54G,
knows the IP addresses of the two DNSs. Is there any reason to prefer
this one DNS approach over the other?

Your router _probably_ implements what's known as a caching name server so will
remember results of previous DNS queries for however long the TTL for that
domain name is set to. This should be more efficient and result in less network
traffic than using your ISP's DNS servers directly. If you query the same name
twice in quick succession then your router will query the ISPs name server the
first time then remember the result for the next time it's asked the same
question.

[Fred Blau]

Thanks, Trevor and Bob. I'll keep only the router's address in resolv2.

My very quick search on Linksys' website found nothing about caching
name server.



On Fri, 25 May 2007 18:16:08 UTC, "Trevor Hemsley"

Post by Trevor Hemsley
On Fri, 25 May 2007 14:39:08 UTC in comp.os.os2.networking.misc, "Fred Blau"

Post by Fred Blau
nameserver <LAN IP address of my router>
and this seems to work just as well. The router, a Linksys WRT54G,
knows the IP addresses of the two DNSs. Is there any reason to prefer
this one DNS approach over the other?

Your router _probably_ implements what's known as a caching name server so will
remember results of previous DNS queries for however long the TTL for that
domain name is set to. This should be more efficient and result in less network
traffic than using your ISP's DNS servers directly. If you query the same name
twice in quick succession then your router will query the ISPs name server the
first time then remember the result for the next time it's asked the same
question.

[Bob Eager]

Post by Fred Blau
domain <name of domain>
nameserver <IP address of 1st DNS>
nameserver <IP address of 2nd DNS>
where <name of domain> matches that in \ibmlan\ibmlan.ini, and the
numerical IP addresses for the domain name servers are what my ISP
provided.
My LAN is a peer network. Today I deleted the first line of resolv2 and
rebooted, then connected to my LAN and saw nothing unusual. I also
connected to the Internet (the LAN has a router between the computers
and the DSL modem) without trouble.

The peer networking doesn't use that directly. If you are using TCPBEUI,
it may end up needing it occasionally. But the first line is just to
give a default domain name for TCP/IP domain names, so that if you
typed:

ping fred

it would expand that if required to

ping fred.my.domain.name

[Fred Blau]

Bob,

Thanks for the clarification.

I am using NetBIOS and TCP/IP, but not NetBIOS over TCP/IP. TCPBEUI is
this last one, isn't it?

Post by Bob Eager

Post by Fred Blau
domain <name of domain>
nameserver <IP address of 1st DNS>
nameserver <IP address of 2nd DNS>
where <name of domain> matches that in \ibmlan\ibmlan.ini, and the
numerical IP addresses for the domain name servers are what my ISP
provided.
My LAN is a peer network. Today I deleted the first line of resolv2 and
rebooted, then connected to my LAN and saw nothing unusual. I also
connected to the Internet (the LAN has a router between the computers
and the DSL modem) without trouble.

The peer networking doesn't use that directly. If you are using TCPBEUI,
it may end up needing it occasionally. But the first line is just to
give a default domain name for TCP/IP domain names, so that if you
ping fred
it would expand that if required to
ping fred.my.domain.name

[Bob Eager]

Post by Fred Blau
I am using NetBIOS and TCP/IP, but not NetBIOS over TCP/IP. TCPBEUI is
this last one, isn't it?

Yes. So, in that case, resolv2 has NOTHING to do with Peer at all!