Why doesn't the subdomain work externally?
 

Hello guys,

I'm new here and I'm trying to setup a subdomain on my domain "neoplaygrounds.com".

I've setup Bind9 and it's working, I even checked logs and no errors - everything is working but I can only find subdomain in dig writing "dig @SERVER_IP cp.neoplaygrounds.com" or "dig @127.0.0.1 cp.neoplaygrounds.com" ( On nslookup I can do a lookup on nameservers & subdomain and works ) but if I try to run dig without @127.0.0.1 or @SERVER_IP it works but it doesn't say "(1 server found)" anymore and on Windows it doesn't even recognize on pinging nor on any browser.

Why that and what can I do?

By the way, here are logs and files if needed:

/var/log/syslog:

/etc/bind/neoplaygrounds.db:

Reverse DNS:

/etc/bind/named.conf.options:

/etc/bind/named.conf.local:

Bump.

Bumping is against the LQ rules and also general netiquette.

I believe you need to put the following information in your httpd.conf (based on some googling):

You will obviously have to enter your own domain and directory structure.

Sorry, I was desesperated. I've been whole night searching and trying new configs lol

By the way, doing what you said I get these errors:

EDIT: After running some codes, Apache2 finally ran without errors but the subdomain still doesn't work.

Here is what appears when I run "dig cp.neoplaygrounds.com":

This is what appears when I do "dig @127.0.0.1 cp.neoplaygrounds.com":

And this is what appears when I run "dig @localhost cp.neoplaygrounds.com":

look at this

[rou@mga ~]$ dig neoplaygrounds.com in ns

; <<>> DiG 9.9.1-P4 <<>> neoplaygrounds.com in ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6825
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;neoplaygrounds.com. IN NS

;; ANSWER SECTION:
neoplaygrounds.com. 86400 IN NS ns1.no1http.com.
neoplaygrounds.com. 86400 IN NS ns2.no1http.com.
----------------

[rou@mga ~]$ nslookup cp.neoplaygrounds.com ns1.no1http.com
Server: ns1.no1http.com
Address: 91.215.156.61#53

** server can't find cp.neoplaygrounds.com: NXDOMAIN

I can't understand what that means ( I mean, I understand that cp.neoplaygrounds.com cannot be found but I can't understand why that ), what can be the problem?

the domain neoplaygrounds.com is registered to work only with ns1.no1http.com
which is not ns1.neoplaygrounds.com

what you have to do is contact registra ask them to point that domain to your
new dns server

after that only you can check the problem one by one

"that domain" - What domain? neoplaygrounds.com or the nameserver ns1.no1http.com?

ns1.no1http.com
ns2.no1http.com

Both are from the server company, not from the registrar. The server company told me that I had to create a DNS server by myself.

yeah that is right you have to create your own,
but they didnt tell you which is you need to inform them
after you done it

so please checking with "whois" command mostly available for linux system
otherwise you have to execute yum install jwhois (for RH family)

"neoplaygrounds.com" is already poiting to the machine, I don't see what you mean by "point to the DNS server" ._. The domain itself works, only cp.neoplaygrounds.com doesn't.

haha so fast you reply me ok then look here

please run whois so you will get like this

[rou@mga ~]$ whois neoplaygrounds.com |grep nameserver
nameserver: ns1.no1http.com
nameserver: ns2.no1http.com

for you please run "whois neoplaygrounds.com"

you have to make change on the domain registra first for nameserver
then all others A record will work

need to change to
ns1.neoplaygrounds.com
ns2.neoplaygrounds.com

until that, your problem will not solve

Oh, ok. Now I understood you. I'll do this and then I'll get back. It will start working after propagation of nameserver change? By the way, what should I put in nameserver IP? The IP of my machine, the IP of the answer from "dig ns1.neoplaygrounds.com" or the ones that are in /etc/resolv.conf?

I'm sorry for all these dumb questions, I'm starting with domain names now...

for /etc/resolv.conf in the server
just need to have as below
nameserver 127.0.0.1

the thing you need to submit to them is

ns1.neoplaygrounds.com ns1_ip_address
ns2.neoplaygrounds.com ns2_ip_address

however once changed in the whois
please allow 72 hours for propagation :)

I still didn't get that. What is the nameserver's IP? The machine's IP?

the ip is the machine ip you install bind
if you have 2 ip in the machine then submit both ip
one become ns1 and the other one become ns2

if you have another machine want to become ns2 is more welcome
mean you have ns1 and ns2 from diffrent machine this way more better :)

Okay, thank you for everything.

It is now working but it is redirecting to main path instead of the path that I've set on httpd.conf, what can I do?

looks good :)

Domain Name: NEOPLAYGROUNDS.COM
Registrar: INSTRA CORPORATION PTY, LTD.
Whois Server: whois.instra.net
Referral URL: http://www.instra.com
Name Server: NS1.NEOPLAYGROUNDS.COM
Name Server: NS2.NEOPLAYGROUNDS.COM

however remember to hold your time for propagation

I know it's working already. The problem is that cp.neoplaygrounds.com redirects to the main path ( /var/www/ ) and not to the custom path I've set in httpd.conf. What can I do?

i try to edit the page before but problem with this LQ now extra info for you
your dns looks good


[rou@mga ~]$ nslookup cp.neoplaygrounds.com 178.238.227.167
Server: 178.238.227.167
Address: 178.238.227.167#53

Name: cp.neoplaygrounds.com
Address: 178.238.227.167


its resolved :)

I think you didn't understand yet the problem: The problem is that cp.neoplaygrounds.com redirects to /var/www/ and not to /var/www/cp/www/. Do you understand now?

yeah i understand i show u what i got

"Oops! Google Chrome could not find cp.neoplaygrounds.com"

this is happen when your dns just join global registry, please hold your time

however you can paste the httpd.conf container for that cp let me see

Oh, okay.

You mean, paste the httpd.conf code here for you to see it? Sure:

I got to change port in 'Listen 80' because with port 80 I got error of Apache.

i think you need to settle this one first dont be hurry
can you show me this result

# cat httpd.conf |grep 80
then we go one by one

Nothing shows, I've tried that before.

ok try now change back to 80 then stop and start apache, any error please post

I get this.

okeh something is using the port now execute this

# netstat -tanp |grep 80
show the output

Nothing appears too.

off iptables if you on
then execute
# setenforce 0

that 0 is 0123 not Orange

then start apache

I didn't get that.

"off iptables if you on" - Disable iptables if it's on?
"then execute
# setenforce 0" - Where? Shell file? Terminal? I don't really get that.

yeah everything in shell

1) # /sbin/service iptables off
2) # setenforce 0
3) # /sbin/service httpd start

My system is Debian, not CentOS :p

okeh no issue
# setenforce 0
# /etc/init.d/httpd start

As I said, my system is Debian. There's no "setenforce" nor Apache2 is called HTTPD xD ( but that I can fix )

my god, i also dont have setenforce ( mageia linux desktop)
for this moment i think need to wait some deb admin to help you on the port 80
since its unable to find with cmd netstat

mustbe something is blocking from internal system which i am not familiar with that
or you maybe need to come out with new topic about this port issue please define debian on your topic

I'm almost certain that this is a bad idea - as far as I understand it, this means that no web browser will connect to your website by default, because they will try to connect with port 80.

I think a more likely fix is to change it back to 'listen 80' and find and kill the process which is binding to 80 already. http://www.linuxquestions.org/questi...7/#post2474057 talks of the same problem (ey have got a subdomain setup too) and mentions as a fix removing the 'listen' line altogether - which you could try, but as ey mention in their post, I don't know whether that's just a kludge.

To work out what's listening on what port, run:

My output looks like:Active Internet connections (only servers)
so you can see httpd (apache for you) listening on port 80 (the :::80)

EDIT: Also just found the docs for the VirtualHost directive: http://httpd.apache.org/docs/2.2/vhosts/examples.html the 'listen' line seems to be a good'un, but it may be worthwhile comparing the relevant sections of your httpd.conf...

Hope this helps,

Nothing using port 80. If I remove Listen 80 and set NameVirtualHost *:80 and <VirtualHost *:80> I get this:

Hm. Well, it sounds like we're getting closer... Can you post the relevant section of httpd.conf as it currently looks?