Re: [fw-wiz] DNS records for a firewall NAT pool

From: Barney Wolff (barney_at_databus.com)
Date: 07/30/03

  • Next message: Carson Gaspar: "Re: [fw-wiz] DNS records for a firewall NAT pool" 
    To: Frank Knobbe <fknobbe@knobbeits.com>
Date: Tue, 29 Jul 2003 18:43:10 -0400

    On Tue, Jul 29, 2003 at 04:55:14PM -0500, Frank Knobbe wrote:
    > On Tue, 2003-07-29 at 12:17, Barney Wolff wrote:
    > > For example, 66.114.72.185 -> p72-185.acedsl.com -> 66.114.72.185 , done
    > > by my ISP.
    >
    > Adding to that, in most cases you get can get away by entering the IP
    > address as the host name in your in-addr.arpa zone. That way the IP
    > address 1.2.3.4 can be mapped to the _hostname_ (as _string_) 1.2.3.4,
    > which of course is typically resolved back to the IP address.
    >
    > So above example would read:
    >
    > 66.114.72.185 -> "66.114.72.185" -> 66.1114.72.185 :)

    I'd be very wary of dots in a hostname, and of hostnames beginning
    with a digit *. FreeBSD's gethostbyname seems to accept a dotted-quad
    as a name, but I'm not sure that's universal.

    * Names starting with a digit are valid in dns but not valid hostnames.
    Some systems care, some don't. 

    -- 
Barney Wolff         http://www.databus.com/bwresume.pdf
I'm available by contract or FT, in the NYC metro area or via the 'Net.
_______________________________________________
firewall-wizards mailing list
firewall-wizards@honor.icsalabs.com
http://honor.icsalabs.com/mailman/listinfo/firewall-wizards
  • Next message: Carson Gaspar: "Re: [fw-wiz] DNS records for a firewall NAT pool"

    Relevant Pages

    • Re: ~/.hosts patch
      ... to hosts as a user or do interesting ssh port forwarding ... feature any user could redirect that host. ... fully-qualified hostnames. ...
      (freebsd-current)
    • Re: Computer host names - recommendations
      ... > I've been searching for some guidelines/recommendations on hostnames. ... in this case a NIS server at an Arizona location. ... As for naming host names by location, I think this is a double-edged ...
      (comp.security.unix)
    • Re: DHCP IP range + auto hostname
      ... option domain-name-servers 192.168.0.1; ... cassiopeia# host diskless131.ronet ... The clients should be able to determine their hostnames using a reverse dns lookup, and the set their hostnames automatically. ... after the machine got its IP address from the DHCP server, it should set its hostname to 'diskless131.ronet'. ...
      (freebsd-questions)
    • Re: DNS: inverse lockup returning multiple host names --- allowed or not allowed?
      ... I'm trying to find out if it is allowed to have several hostnames being ... hostnames returned are primary hostnames from the hosts' point of view. ... inverse lookup, only one of the names returned can possibly be a primary ... primary host name or which one should be used from there on for the ...
      (Debian-User)
    • DNS: inverse lockup returning multiple host names --- allowed or not allowed?
      ... RFC 1034 and RFC 1035 don't seem to answer that question. ... the inverse lookup does return three hostnames that share the same IP address. ... All the hostnames returned are primary hostnames from the hosts' point of view. ... But one could argue that from the point of view of those who do the inverse lookup, only one of the names returned can possibly be a primary host name or that at last it cannot be decided which one is a primary host name or which one should be used from there on for the purposes the request was made for. ...
      (Debian-User)