OVH Community, your new community space.

OVH Domain - KS Server - DNS Questions

20-10-2013, 09:35
Hey Jumbo,

Editing the posts here and removing the link will not get google to drop your result.

If you don't want google indexing you, you have a few options here:

1) Redirect the page to the correct location (301 response)
2) Request a removal from Google
3) Return a 404 (Google generally removes dead links)
4) Block them via robots.txt
5) Return 410 Gone (While this will remove you from Google, it may take Google longer to check back to re-index or it may not at all, you may need to resubmit if you intend to use the domain again)

If your just worried about a page which will be updated quite soon, just leave it and update it when ready, Google will update it's index quite soon after you have updated your website again (or it usually does)

Hope this helps :-).

19-10-2013, 17:54
Greg: I know it's not a big issue for you, but google has now indexed the previous page as the top result for my website - I was initially hesitant to post my domain on this forum because of that very reason. Is there any chance you could edit your post(s) to remove my domain name?

I'm intending to host my website and blog seperately (the blog runs on nodejs), as well as a few web applications I'm writing; one of which utilises ffmpeg for video conversion (hence I need good CPU speed). Mainly just a hackbox, but I like some power behind what I'm doing, so I got a 16G instead of a 2G.

I used to have a smaller box and I learned loads about sysadmin stuff from that, so now I'm scaling up. I'd love to get into virtualisation and how that all works. Maybe a little down the line...

19-10-2013, 13:44
Anytime, glad I could help
Purely out of interest, what are you using the KS16G for?

I turned mine into a proxmox host and run a bunch of virtual machines on there, it handles them beautifully

I have different VMs for different purposes and even different web sites. It was great fun putting it all together and getting it running

19-10-2013, 13:33
Hey Greg, it's working, thanks very much for the help. I can now use virtual hosts to control subdomains using mod_rewrite!

Thanks a lot for your help, very much appreciated

19-10-2013, 00:45
It's working
google domain name servers and openDNS domain name servers both give the correct result

dig @

; <<>> DiG 9.9.3-rpz2+rl.13214.22-P2-Ubuntu-1:9.9.3.dfsg.P2-4ubuntu1 <<>> @
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6517
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

; EDNS: version: 0, flags:; udp: 512
;. IN A

. 21418 IN A

;; Query time: 26 msec
;; WHEN: Fri Oct 18 23:41:00 BST 2013
;; MSG SIZE rcvd: 64


19-10-2013, 00:29
I've updated the nameservers to:

Originally I changed these to the ovh / ks dns as I thought I had to.

So a 48 hour wait then

19-10-2013, 00:18
Ignore the bind stuff if you are not using it.

I notice that you say your DNS shows

Open your OVH Manager V3
click on the domain
Domains & DNS
DNS Servers
Delete the records in there
Click Validate
When you have done that let me know, I am following the thread so it will email me.

This should fix the issue.
It will take up to 48 hours to propagate, but you can check instantly if you try

Give it a few minutes before you do this so the OVH servers have time to update via cron.

18-10-2013, 23:49
I've changed the settings in /etc/bind/named.conf.options (never seen this file before actually), from:

listen-on port 53 { ; };
listen-on-v6 { ::1; };

to the ones you suggested. Restarting bind9 gives the following error:

rndc: connect failed: connection refused

For the record I haven't set up any extra dns stuff on my server, and I haven't changed any other settings really. A quick google says the above error is a permissions problem, but I don't have a group called "named" it seems.

18-10-2013, 23:17
dig any

; <<>> DiG 9.9.3-rpz2+rl.13214.22-P2-Ubuntu-1:9.9.3.dfsg.P2-4ubuntu1 <<>> any
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

You don't appear to have a DNS server running on your server. If you have, check /etc/bind/named.conf.options for
listen-on port 53 { any };
listen-on-v6 { any };

If they are not there, add them. They should be but may have instead of any. Replace { }; with { any };

The DNS server provides the correct information.

You're almost done

Just make that change then
service bind9 restart

18-10-2013, 23:02
For the above: domain is

Hi gregory, thanks for the reply.

I have added your wildcard dns setting as you suggested. The settings now look like this: A
* A

The NS settings are what concern me. In this "zone" section, they still say anycast (a whois to the domain disproves this though): NS NS

Even with the new wildcard added above, the domain still does not resolve. Do you have any other suggestions?

18-10-2013, 22:56
What's the domain? I will check it my end and see what IP I get.

18-10-2013, 22:10
You need to set wildcard in the DNS
* A

Do this /after/ any strange IPs such as if you have a failover IP so they resolve correctly: in a
* in a A
* A

Save the cname for something useful, it just adds another call to a DNS record.

As for the apache stuff, I do it as follows:
Any subdomains
The domain
Default - "This is the default landing page"

// file /etc/apache/sites-available/

ServerAlias *
DocumentRoot /var/www/

// file /etc/apache/sites-available/

ServerAlias *
DocumentRoot /var/www/

// file /etc/apache/sites-available/

ServerAlias *
DocumentRoot /var/www/

// file /etc/apache/sites-available/catchall.conf

ServerAlias *
DocumentRoot /var/www/default

The catchall.conf one will grab every other attempt to connect with apache, whether it is by http://ip or a fake connection such as telnet 80 GET "http://idontexist HTTP/1.1"

I would also consider putting the virtualhost stuff in one file so you can ensure the correct order is followed. It is easy to forget to set the correct loading order in /etc/apache/sites-enabled/ -> ../sites-available/ -> ../sites-available/ -> ../sites-available/
9999-catchall.conf -> ../sites-available/catchall.conf

18-10-2013, 21:54
Hi guys, I have a few questions about DNS / server settings and I was hoping someone could help me set up properly.

My use case:

- I have previously bought a domain through ovh.
- I would like to host this on my dedicated kimsufi 16G server.
- I would also like the ability to create a subdomain, namely in the near future.

If I read right, I can use Apache to do this (it would be great if I could do this via Apache) - I'm currently attempting to use virtual hosts to do this, to no avail (I think first and foremost my dns settings are wrong)..

The first issue which led me to posting here: my domain does not resolve even though I changed the dns settings over 48 hours ago. Technical support directed me to these forums -.-

Here are my dns settings (according to Domains & DNS):

Great. Now if I go into "Dns Zone", it looks like this (wtf):

NS A my-kimsufi-IP-address CNAME

So there are some discrepancies there...

I won't go onto Apache vhost stuff yet, but (if I understand correctly), I want to be doing something like this:

// file

DocumentRoot /var/www/

// file

DocumentRoot /var/www/


1. What's up with the dns discrepencies? Are they even correct?
2. What am I doing wrong