Re: INN on Enterprise Linux 4

On Sun, 24 Jun 2007, in the Usenet newsgroup linux.redhat, in article
<f5ku0m$da9$1@xxxxxxxxxxxxxxxxxxxxx>, Gregory Baxter wrote:

"Moe Trin" <ibuprofin@xxxxxxxxxxxxxxxxxxxxxx> wrote

The _usual_ problem is DNS name resolution. The server attempts to look
up the name of the host that is connecting, and the nameserver isn't
responding in a timely manner - either because you are asking a name
server that isn't running (look in /etc/resolv.conf), or the name
server is mis-configured.

Excellent call on that one. I set up the server a few weeks ago and our
corporate guys changed the DNS servers since then

and the reason they decided to do this is...

I really don't understand why people are playing musical IP numbers with
the name servers. We've been using the same IP address for the name
servers since we started using DNS over twenty years ago. We're still
using the same subnet concept, even though who has what subnets has been
changed a few times. My primary workstation has changed IP address four
times in the 16+ years I've had this hostname. Sigh...

but since most everyone gets their TCP/IP configuration from the DHCP
servers they neglected to inform anyone.

Sounds like a MCSE. Our systems to not go wandering in/out of the
building, and thus have fixed addresses. The person installing the
software has a piece of paper that lists hostname, IP, DNS and
authentication server addresses, and plugs in the appropriate values.

NNTP-Posting-Host: ustr-baxtergt.na.uis.unisys.com

Our security people would be freaking out over that. If that is
actually the hostname, you may want to have a look at RFC1178, and
specifically the top of page 3. We require our users to submit a
preferred (and two alternate) hostname when they register their "new"
computer (before it is allowed on the wire). Names are caseless
alphanumerics, and must begin with a letter and can include an
embedded dash. We explicitly recommend not using numeric or easily
confused names, and suggest users follow their department naming
scheme. That scheme uses names in a series of

Cars Beers Navel vessels Battles
Countries Animals Film/Stage/TV Stars Athletes
Stars/Planets Flowers Fruit/Vegetables Sports Teams
Chemicals/Elements Newspapers Magazines Publishers
States/Provinces Oceans/Seas Diseases Mythical Names
Cities Firearms Satellites Disasters
Cartoon Characters Pasta Kings/Queens/Presidents Wines/Wineries
Painters Zodiac Currencies/Coins Scientists

Even with over 2500 hosts in this subdomain, our users can come up with
some "interesting" (or at least unique) names.

Old guy
.

Relevant Pages

  • Re: Exchange Help!!!!
    ... Best not to have your ISP host your DNS, ... up on the Qwest Servers before actually changing the name servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: [opensuse] round robin dns for the repo mirrors
    ... balancing scheme for the repo mirrors. ... dns loadbalancer that selects from a pool of physical servers. ... Well, that's DNS round robin. ... Use 'host' and look at the ...
    (SuSE)
  • Domain Setup
    ... I have to host 3rd party software over IIS using SSL. ... Could someone give me a link to setup the DNS to host ... forwarding through the router to my servers LAN IP addrss. ...
    (microsoft.public.windows.server.dns)
  • Re: How to disable the "implicit mx record" in Exchange
    ... where these hosts are not actually mail servers. ... MX record host, and sometimes it is sending to the host with the A record for ... So when Exchange gets a DNS timeout looking up an MX record, ... I feel that this problem is a combination of saturated bandwidth causing DNS ...
    (microsoft.public.exchange.admin)
  • Re: Transfering domain authority
    ... I'm not saying you can't host your own, I do that, but I have three DNS ... servers, two of which answer only to the public requests. ...
    (microsoft.public.win2000.dns)