Hi There,

Let me start by saying I have been very impressed with the expertise in this forum. It has helped a lot.

I am running Redhat 6.2 with Apache and DNS and I am very close to the ideal system I want.

I have tested the DNS and it Works great (If you are connected to the same Lan and have it as your only name server).
To test I used ONLY that DNS I can get other peoples sites as well as the ones I configured for use in Apache.


After I thought I had the box totally configured I went ahead and registered a domain name to use for the name server. I registered "jubrosworld.com" and of course they required the IP to my server - no problem.

I then pointed my domains to that nameserver : ns1.jubrosworld.com

(I know I need a secondary - so I just pointed it to some big local ISPs for now)

I waited for everything to propagate then I started testing. I was unable to pull up any of the sites that I had pointed ns1.jubrosworld.com


THE PART THAT CONFUSES ME is that I have a zone configured for a domain that is called www.softwarejedi.com and FOR SOME REASON comes up on screen served out by my Apache if I enter "ns1.jubrosworld.com" into the BROWSER and not by its regular URL. This is Bizarre .

To recap:

www.softwarejedi.com points to ns1.jubrosworld.com as its name server

ns1.jubrosworld.com points to the IP of my DNS.

The DNS on the internal Network is 192.168.1.3 (once it is through the router - the router causes no problems)

The search order was hosts then DNS and I think this may be how the softwarejedi site got served up because in my host file I also had (my other domains are set to resolve through the DNS and this one) :


192.168.1.3 www.softwarejedi.com

certainly the router sends the DNS request to 192.168.1.3 but the entry in the Browser was : http://ns1.jubrosworld.com and that should bring up nothing.

At any rate the DNS does not seem to be searched and in this case the host file was somehow used to send me that page. There is no other way for me to have gotten that page because I was EXTERNAL the Network.


I know I am close and I feel it may have somethng todo with my resolv.conf file which has been untouched during the whole process.

Essentially I am trying to configure my DNS so that it works when requests are made to ns1.jubrosworld.com What should my resolv.conf file look like?


Note that I have running tests from different networks entirely to make sure I was EXTERNAL and please note that I have it working internally where the DNS will serve out at least 6 differnt sites/zones that I have configured for Apache. The DNS will also go find/cache other domains you ask for such as www.google.com.

The focal point Is that I am unable to resolve anything externally except for that bizarre connectivity to the my DNS by entering the name of my nameserver into the browser.

I AM CLOSE - Please help me fill this gap in my knowledge.

thanks in advance

fed007









This tells me that there is external connectivity to my DNS but also that the resolving is somehow buggered up

i'm sorry to say i can offer little in terms of a solution to your problem. however, i do have a question for you.

i'm interested in setting up a DNS server myself due to the fact that my cable company has disabled port 80, and i'm yet to find a nameserver out there that will forward to a different port.

the only solution i can think of at this point would be my own nameserver (something i've been interested in for quite some time, as well). i was curious as to how you set yours up and how exactly one would go about creating a public nameserver.

i would appreciate any insight you can offer. thanx in advance.

HahHah!!!

I had this same problem for *cough* a couple of weeks way back when. It's a question of terminology. The whole thing gave me nightmares as it appeared to be a chicken and egg problem. "I want to resolve names for my web server, but I can't point my domain to my nameserver".

In short - you first must register your name server. This is a separate process from just pointing your domainname to your name server. Forget about pointing domain names to it right now. Get the TWO name servers registered. wait about 24-48 hours for the changes to be made. Then point your domian to your newly registered name server. Wait another 48 hours for changes to be made and to propagate.

You need to ask your ISP to host a zone for one of your name servers. Some allow a web interface to do this.

The reason you are getting the 'wrong' domain name is that your resolver (/etc/resolv.conf is pointing at either your ISP's name server or your name server. (I think it's your nameserver - not too sure yet...)

I just tried to resolvither your ISP's name server or your name server. (I think it's your nameserver - not too sure yet...)





@!*&@#%^*@&#%*@ BRAIN-DAMAGED paste in Mozilla!!!!! I'll post from nutscrape in a sec....

(@#@*%*$@ piece of (&*^*&%^(*&%)

Here's the results of your domain...And here's a non-existant domain reply

questions:
1) where does one register a nameserver?
2) is it possible to register just one? (was planning on having the second nameserver pointing to my domain be that of my isp)
3) what do you mean by contacting my isp and setup a "zone"? i have no clue...
4) how do you actually setup the nameserver itself?

First off a name server won't solve your ISP blocking port 80 access. On top of that, if you raccount is inbound 80 blocked then you probably have a dynamic IP and a name/http/ftp/news/mail server is outside the acceptable use policy of your ISP. (One big US ISP actually only allows sending mail via _their_ mail servers - port 25 outbound is blocked.)

Answer to question 1: You can register a name server at most of the larger registrars and in your case it won't work. You can try dyndns.org.

Questions 2 + 3: See answer 4.

Answer 4: Somewhere around here there is a link to the fine book <nerd humour>I would say the authoritative source </nerd humour> by O'Reilly press called DNS and Bind by Ablitz and Liu. (Dig around at oreilly.com) Read up as it's gonna explain the whole thing. When you think the reading gets difficult - have a look at Sendmail (also from O'Reilly). It will make DNS and Bind look like Curious George.

thanx for the info. however, my isp does not have any problem with my running an http, ftp, mail, or news server. they simply shutdown port 80 due to code red. and i am positive that i have a static ip (it's been the same for the 5 months i've had cable).

thanks for the suggestion on the book... i'll go check it out tonight. though (and i could be wrong) i heard it was possible using your own nameserver to parse your domain out to an ip AND a specific port. i'm running apache on port 82, and it works fine except that 82 isn't the default http port (duh).

Don't be fooled by this same IP for the last so many months. Unless you were given a Static IP to assign your machine, most likely you have a dynamic. As I use to work for Road Runner, we would get calls all the time of people complaining their IP changed, we would tell them they never had a static IP, its just whatever the server will assign, it just so happens most would keep the same IP for so many months.. sometimes up to a year then be suprised when it did change. So I would confirm this with your ISP first before assuming.

Syncrm

Can I suggesting kicking your ISP's @$$? code red will only attack WIN2K boxes running IIS, that are UNPATCHED.. Microsoft has released a patch that "patches" things up nicely, rendering the code red "not a threat".
Ridiculous reason to restrict port 80.

i couldn't agree more. but despite my objections (many times in unmentionable words. hehe.) they insist on keeping port 80 blocked. they claim that every time they open it back up, their server machines are infected by code red from the network users. to this, i say:

1) don't use windows (reasons should be pleantiful as to why it's a lame os)
2) install the $#&@ing patch!!!

it took me all of 20 seconds to install the patch on my win2k machine... which really wasn't even necessary since i don't run IIS and am behind a firewall. either way, it's some bullsh*t.