forum.excito.com

Ok, so the \r\n line endings did you in. Next time, run dos2unix on your file to remove these.

Oddly, you suggested that you did not alter the script (and it worked begore and not now), but now you mention that you did edit it in conTEXT. Thats a bit of a contradiction???

just for fun, can you add the line at the top of your script?

Also, is there any chance you edited this file in windows?

Well, RIPE tells me the PTR records of the name servers were not reflective of the forward records. My guess is this is a quirk from powerDNS which does not understand bind-host. Anyway, I changed the reverse records to match the forward records. . EDIT: I ran a few hostnames over https://www.whatsm...

This is something that should be addressed though. It just seems there is something wrong with the glue records in the myownb3.com domain that these ISPs don't carry it anymore. Do you have the name server IPs?

There iscurrently no development for this package. Once the new owners of Excito are operational they are the best people to ask. The community has very limited development capacity.

Do you mean this?
http://install.mybubba.org/latest/b3/

Please start a new topic on this. If you get 'update siccessful' or something like that then the easyfind code is not the problem here

If you do not type exactly what you did and what the responses were I'mnot going to bother reading it.

If you can log in during the green period and break the instaaler before it goes green, then why not change the installer to only set up the ssh nvironment and the ability for end user to run the rest manually. That should solve so many install problems.

ah this could be because you only changed the records in the zone file, but did not specifically change them at he registrar as well. For .com domains this is sometimes necessary.

replication issue fixed and tested for domain-record 1544

Thanks. Good report. I'll try to see why the slave isnt updating asap

You did not get an answer, This means your local DNS server (192.168.1.254) is buggered. You should get this: [root@php-sites ~]# dig -t ns myownb3.com ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6 <<>> -t ns myownb3.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: N...

Ns1.mybubba.org will not act as a recursive ns, so setting ns1.mybubba.org in resolve.conf would be foolish. However he's not getting the wrong ip, he's getting a failure to resolve. Its almost like he's still asking the old nameservers. In that case, try dig -t ns myownb3.com and see what that give...

the problem is on your end. My guess is that you first pinged your machine, and then updated easyfind. This first ping loaded the cache of your upstream DNS provider, and thus it takes a while for the change to propagate. C:\Users\ubi>ping su****drobert.myownb3.com Pinging su****drobert.myownb3.com ...