Non-Octet Boundary Delegation (RFC 4183)

Станислав ginermail at
Thu Sep 22 11:56:50 UTC 2011

On Thu, Sep 22, 2011 at 10:58 AM, Simon Hobson <dhcp1 at> wrote:
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> Stas wrote:
>> Thank you Simon, thank you Andris.
>> Andris, problem is that in that case I will need to use "nslookup
>> instead of "nslookup" to
>> get DNS record.
> You **ALWAYS** lookup by the normal IP - eg dig -x
> That results in a lookup of
> The trick is that instead of that being a PTR to some FQDN, it is a pointer
> to
> Ie, in the zone there'll be a record
> 68 PTR
> Then in the zone, you have an entry dynamically created
> by DHCP which is " PTR <some fqdn>".
> It's some time since I played with this, but I recall it "just works" -
> looking again at RFC 4183, I certainly didn't do it that way. But I'm happy
> to be corrected if I'm wrong.
> --
> Simon Hobson
> Visit for books by acclaimed
> author Gladys Hobson. Novels - poetry - short stories - ideal as
> Christmas stocking fillers. Some available as e-books.
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at

I went though the RFC 2317 and tried to configure bind and dhcpd in
some ways but I didn't reach appropriate result.

I need to have reverse records for (from to been resolved by our dns server but other networks (all
of except of need to be resolved by
upstream DNS server and I'm not sure how it's possible to configure
BIND + DHCPD for it.

In case I use configuration suggested by Andris it doesn't resolve
names by IP addresses.

** server can't find NXDOMAIN


More information about the dhcp-users mailing list