[nos-bbs] JNOS DNS PROBLEM

[Michael Fox - N6MEF]

He said he changed his router.  So I would start with what could be wrong there.  Does the new router need a route to the JNOS 44.x address via the linux address?  Does the new router allow UDP port 53 allowed to your JNOS machine as well as your linux machine?  

 

Look at tcpdump on the jnos-to-linux tunnel, the linux Ethernet port and look at the logs in the router to find out where the packets are dying.

 

M

 

From: nos-bbs-bounces at tapr.org [mailto:nos-bbs-bounces at tapr.org] On Behalf Of Chris
Sent: Friday, November 25, 2011 5:14 PM
To: TAPR xNOS Mailing List
Subject: Re: [nos-bbs] JNOS DNS PROBLEM

 

Look at your linux system IP, I bet the network changed. Then look at the autoexec.nos carefully and be sure your nameservers, routes, and tunnel lines have IPs that make sense.

Would need the output of ifconfig -a on the Linux box, the autoexec.nos file and likely the domains.txt file in order to give specifics. 

On Nov 25, 2011 8:00 PM, "Y. Robert Sismanyan" <ve2har at videotron.ca> wrote:

Hello,

Due to some changes from my ISP I had to replace my old Linksys router model BEFW11S4
to a new model Linksys router model Cisco E3200.

After this change my JNOS domain server is not working anymore; when I enter any domain
name is unable to find the IP number. In autoexec.nos, domain server IP numbers are up to date.
I am running RedHat 7.2 Enigma and domain translation in linux is working fine, but not with JNOS.

I appreciate any help. Thanks.

Robert, VE2HAR


_______________________________________________
nos-bbs mailing list
nos-bbs at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20111125/cc305aa1/attachment.html>