[openbeosnetteam] Re: DHCP Client needed,what would stand in the way?

From: "Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx>
To: <openbeosnetteam@xxxxxxxxxxxxx>
Date: Thu, 31 Jul 2003 14:25:12 +0200

> I have a small suggestion here and also a question.
> Calling the setting "nameserver" is a bit ambiguous, maybe it should
> be called "dnsresolver", "dnscache" or something similar. Not even
> MS calls it nameserver anymore.

Does not resolv.conf use "nameserver"? I thought that would be ok, then.
"dnsresolver" is ok, too.

> Now for the question....
> Why separate sections for ipv4 and ipv6 in the dns configuration?
> A given query, say for an MX record, will return the ipv4 address
> and also the ipv6 address in the same result set, regardless of wether
> the dns cache used is on a ipv4 or ipv6 address. The only exception
> to this rule are queries for AAAA records wich of course only return
> ipv6 addresses. Having separate sections for ipv4 and ipv6 doesnt
> make any sense to me.

You must specify the IP addresses of each nameserver. I thought IPv6
addresses for those servers should be added to their own section because
they have another format (than IPv4).
This is just the implication of having many protocols and possibly having
different DNS servers for each protocol.
My thought was that somehow our netstack must know which entry belongs to
which protocol.

> > The DHCP client module would look for all interfaces that have "dhcp"
> > "enabled" (eth1) and begin getting the ip and a nameserver. Those
> > values would be saved as dynamic attributes.
> IMHO, having different dns caches on different interfaces only adds
> unnecessary complexity. How would the resolver library know wich cache
> to use for a given query? Since you dont know ahead of time what the
returned
> result, ie ip address,  will be i cant see any way that you'd know wich
> one to use.

What I meant was:
1) The DHCP module gets the ip and dns.
2) DHCP saves the ip entry as a dynamic IPv4 attribute in the interface
module
3) DHCP saves the DNS entry as a dynamic IPv4 attribute in the DNS interface
module (i.e., it does not belong to the interface, but is a global entry).

Waldemar

Follow-Ups:
- [openbeosnetteam] Re: DHCP Client needed,what would stand in the way?
  - From: Lars Hansson

References:
- [openbeosnetteam] Re: DHCP Client needed,what would stand in the way?
  - From: vladimir reikine
- [openbeosnetteam] Re: DHCP Client needed,what would stand in theway?
  - From: Waldemar Kornewald
- [openbeosnetteam] Re: DHCP Client needed,what would stand in the way?
  - From: Lars Hansson

[openbeosnetteam] Re: DHCP Client needed,what would stand in the way?

Other related posts: