• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Dns info does not propagate

Torsten_Rüger

New Pleskian
I recently set up a domain just the same way as a previous one. The old works, the new not.
On the ui level they look the same and i have no idea why they are not:

plesk db "select * from dns_zone where id>12"

| id | name | displayName | status | syncSoa | syncRecords | email | serial | external_id |
| 13 | rubyclerks.org | rubyclerks.org | 0 | true | skip | [email protected] | 2015050605 |
| 15 | salama-vm.org | salama-vm.org | 0 | skip | skip | [email protected] | 2015051004 |

I cut out some stuff after email that is the same for both.

What i wonder is what the syncSoa=skip means and why it would be there ?

Thanks
Torsten

PS: i did have this issue http://talk.plesk.com/threads/soa-serial-0-domain-will-be-switched-off-off-soon.332780/
 
hmm, maybe i should clarify what "works" means. The domain info does not get propagated, as dig will show

torbook:salama raisa$ dig rubyclerks.org +nostats +nocomments +nocmd

; <<>> DiG 9.8.3-P1 <<>> rubyclerks.org +nostats +nocomments +nocmd
;; global options: +cmd
;rubyclerks.org. IN A
rubyclerks.org. 86382 IN A 192.30.252.154
rubyclerks.org. 86382 IN A 192.30.252.153

torbook:salama raisa$ dig salama-vm.org +nostats +nocomments +nocmd

; <<>> DiG 9.8.3-P1 <<>> salama-vm.org +nostats +nocomments +nocmd
;; global options: +cmd
;salama-vm.org. IN A
 
Hi Torsten_Rüger,

you seem to forget, that your initial nameserver is not your Plesk server, but the nameserver from your domain provider ( vautron.de ), where you registered your domain. At the moment, your domain "salama-vm.org" does not resolve to any IP.
 
Last edited by a moderator:
I bought both domains from hetzner.de , both have the same nameservers set, specifically ns1.first-ns.de
Both act as master in plesk and (in my understanding) should transfer the setup to ns1.first-ns.de

If you do the dig with @rubydesign, you can also see that they both respond identical.

Maybe you are right and i am misunderstanding, and i should ask hetzner. It's just that "skip" that got me alerted.
 
Hi Torsten_Rüger,

at the moment, I can't confirm your settings to be correct. If you check for example with "digwebinterface.com", you will see, that there are no current A - entries for "salama-vm.org" ( which might change within the next 48 hours, due to recent changes ). If you recently changed your settings over the nameserver from Hetzner, please be aware, that the changes might take up to 48 hours, untill they appear.

dig @ns1.first-ns.de salama-vm.org
; <<>> DiG 9.9.5-3ubuntu0.2-Ubuntu <<>> @ns1.first-ns.de salama-vm.org
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 18
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;salama-vm.org. IN A

;; Query time: 8 msec
;; SERVER: 213.239.242.238#53(213.239.242.238)
;; WHEN: Tue May 12 21:34:07 CEST 2015
;; MSG SIZE rcvd: 42

dig @robotns2.second-ns.de salama-vm.org
; <<>> DiG 9.9.5-3ubuntu0.2-Ubuntu <<>> @robotns2.second-ns.de salama-vm.org
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 55962
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;salama-vm.org. IN A

;; Query time: 7 msec
;; SERVER: 213.133.105.6#53(213.133.105.6)
;; WHEN: Tue May 12 21:35:14 CEST 2015
;; MSG SIZE rcvd: 42

dig @robotns3.second-ns.com salama-vm.org
; <<>> DiG 9.9.5-3ubuntu0.2-Ubuntu <<>> @robotns3.second-ns.com salama-vm.org
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 3236
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;salama-vm.org. IN A

;; Query time: 9 msec
;; SERVER: 193.47.99.3#53(193.47.99.3)
;; WHEN: Tue May 12 21:39:44 CEST 2015
;; MSG SIZE rcvd: 42
 
Hello,
thank you for staying with me here. So we are finally on the same page. This is exactly my problem.
I have made the changes last week, so they just are not propagating.
If you dig my server, so @rubydesign, you'll see

dig @rubydesign.fi salama-vm.org +nostats +nocomments +nocmd

; <<>> DiG 9.8.3-P1 <<>> @rubydesign.fi salama-vm.org +nostats +nocomments +nocmd
; (1 server found)
;; global options: +cmd
;salama-vm.org. IN A
salama-vm.org. 86400 IN A 192.30.252.153
salama-vm.org. 86400 IN A 192.30.252.154
salama-vm.org. 86400 IN NS ns1.first-ns.de.

which is the same for rubyclerks.org. So the settings are the same, but salama-vm does not work as it does not propagate.
I have issued a ticket with hetzner, i couldn't say if this problem is on my server (the "skip" flag?) or theirs.
 
Hi Torsten_Rüger,

just to be sure again, I repeat myself in telling you, that not your rented server ( the one with Plesk ) is your initial nameserver, where you have to make your DNS entries. You have an additional login at Hetzner, where you have to add/edit settings for your rented domain(s). I think it is "https://robot.your-server.de/login/index", where you have to login and add/edit, but please check this with the Hetzner Support.
 
Yes, i understand that.
I have set up the domain in hetzner exactly like the rubyclerks one. And that one works while salama-vm.org does not.
Can you say what the "skip" flag from my very first post means ?

Torsten
 
Ok, i got it.

It was a silly little setting at hetzner, which to my embarrassment i had forgotten.

Thank you for the assistance (it did actually help) and if you were closer i'd send you a beer!
 
Back
Top