Private network DNS setup problems

Barry Margolin barmar at bbnplanet.com
Mon Oct 25 23:10:39 UTC 1999


In article <7v2hf3$8gt$1 at eve.enteract.com>,
Dave Kaylor <dkaylor at poboxes.com> wrote:
>oooh!  Reply to group worked !
>
>Just want to update, I went in and found the syslog (thanks to the group)
>and found an error with "ndc restart".  It showed there was an error in the
>named.conf file "near ^M" which was confusing to me.  All I could figure was
>that there was an invisible (control) character embedded in the file.  I
>deleted named.conf and rewrote it and all worked.  There werre only a few
>problems afterward but they went quickly with the use of the syslog.

^M characters usually result from editing a file on a Windows machine and
then transfering it to Unix in binary mode rather than ASCII mode.
DOS/Windows using ^M^J as the line break sequence, but Unix just uses ^J,
so the ^M is treated as an ordinary character by Unix.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


More information about the bind-users mailing list