When I register a domain and get hosing on different company I have to add the hosting company nameserver. This might sound reasonable.
BUT, in the hosing company cpanel there would be NS records with their nameservers, why is this needed ? Also the same if I leave the default nameservers in my domain there are NS records in the DNS section pointing to the same nsx.blabla.com.
Here is a photo explaining what I mean:
https://i.stack.imgur.com/kGy9O.png
So when a request to my domain is made, a final A record is needed. In order to obtain that record, the requester looks up for A record by asking whom? The nameseever added in the liat above or the nameserver in the NS record ?
So when a request to my domain is made, a final A record is needed. In order to obtain that record, the requester looks up for A record by asking whom?
By asking domain NS where pointed the NS records then ask this server(ip on which NS records are pointing) where pointed domain A or AAAA record.
Related
So i have a mail server say "mailer.com". Postfix handles mail for mailer.com also for "virtual.com" (postfix virtual domain).
So, when i create the DKIM key pair:
opendkim-genkey -s mail -d example.com
Which domain do i use here? mailer.com or virtual.com?
Then i put the public key in TXT record on the virtual.com domain?
FYI I used this guide:
https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-dkim-with-postfix-on-debian-wheezy
You need to create keys for each domain you want to sign messages for and put appropriate DNS records in each domain DNS zone.
I'm having trouble verifying namecheap domain with firebase hosting
Tried to follow this posts instructions without success:
Unable to Verify Custom Domain with Firebase Using Namecheap
and this
Adding custom hosting domain: "Unexpected TXT records found. Continuing to watch for changes."
So my definitions are like this:
Type: TXT Record
Host: #
Value: globalsign-domain-verification=...
TTL: Automatic
Type: TXT Record
Host: #
Value: firebase=mydomain.info
TTL: Automatic
Type: CNAME Record
Host: www
Value: myprojectname.firebaseapp.com.
TTL: Automatic
Type: A Record
Host: #
Value: First IP Address retrieved with MXToolbox
TTL: Automatic
Type: A Record
Host: #
Value: Second IP Address retrieved with MXToolbox
TTL: Automatic
When I execute "dig -t txt +noall +answer mydomain.info", it returns:
mydomain.info. 1798 IN TXT "globalsign-domain-verification=..."
mydomain.info. 1798 IN TXT "firebase=myprojectname"
(It has the extra dot at the end of the domain)
But still in firebase dashboard I have this message:
Verifying ownership
Unexpected TXT records found. Continuing to watch for changes.
and later:
Verification failed
Couldn't find the correct TXT records in your DNS records
I'm trying to solve this problem for several days now.
After not having my domain verify for over 24 hours and trying numerous things, I eventually deleted the CNAME record of [projectname].firebaseapp.com. A few minutes later, it verified with no problem.
These are the steps that they want you to do:
Only have the TXT Record for the verification.
After verification, add two A Records.
This is what I did:
Add TXT record and two A records.
Get verified
Hope this helps. I submitted a ticket to firebase to propose that they modify the instructions to make it clear that you can't put the CNAME to your project URL.
Strongly recommend that you contact Firebase support. I had a similar issue going on for days and only after they manually intervened behind the scenes it was resolved. Good luck...
I was facing the same problem. instead of domain, I used # in host and it worked. I am on a Free plan.
Always ensure that you are using a paid version of Firebase. Domains do not get verified if you are using a free account. I had to downgrade one of my old projects in order to verify my new project. Apparently, firebase allows only a certain number of projects to be upgraded to a blaze plan. I hope this helps.
How do i configure my DNS record to point to galaxy?
I bought a domain with the following attributes:
Type: CNAME Record
Host: www
I am kinda lost here, I don't know where I should actually configure my DNS. In my project, or the website I registered my domain in? and how?
The following is my host records:
In Galaxy
Log into galaxy
Click on your app.
Click on settings.
In domains, click add new domain and enter your domain
In the description for the Domains and Encryption section you will see an address that looks something like us-east-1.galaxy-ingress.meteor.com. Copy this down.
On your host
Create a new custom resource record Name: *, Type: CNAME, Data: us-east-1.galaxy-ingress.meteor.com (or paste yours if it differs in galaxy).
Create a new custom resource record Name: www, Type: CNAME, Data: us-east-1.galaxy-ingress.meteor.com (or paste yours if it differs in galaxy).
Let me know if you have any questions! There is a bit more to a full deployment, the docs on http://galaxy-guide.meteor.com/deploy-guide.html go in depth on how to setup everything else.
I have a WordPress site called: www.myfirstwp.com.
I want to transfer it's database to new domain which is www.mynewwp.com.
I did it by exporting the DB from www.myfirstwp.com and imported it to www.mynewwp.com
But in this new site ( www.mynewwp.com ) database have all old one database URL.
So, How can I change entire url of old one (www.myfirstwp.com) database in new one ( www.mynewwp.com ) database? Is there any way to do this?
Thank You.
Update Question :
I have an issue in WordPress. When I try to importing XML file with Attachments it's showing me following error message :
Error Message :
Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator and inform them of the time the error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. Apache Server at mysite.com Port 80
what should I do to solve this type of error message as I am a new user in WordPress.
Thank You.
NOTE: before you tinker with your database be sure to grab a backup first. You do not want to mess up a production database.
The simple way is to open the database on your new domain, open {$prefix}_options and change the home and siteurl rows to reflect the new domain.
This approach works and allows you to operate the site at minimum. The other problems include:
Embedded media links which use the old domain
Other post meta fields and option fields that may contain the old domain.
What I do when this happens is to use raw SQL inside phpMyAdmin (or similar) to search and replace. The following queries take care of post meta and options (95% of the time):
UPDATE wp_options SET option_value = REPLACE(option_value, 'olddomain.com', 'newdomain.com');
UPDATE wp_postmeta SET meta_value = REPLACE(meta_value, 'olddomain.com', 'newdomain.com');
The following tables and columns usually have contained domain references in WP:
wp_options.option_value
wp_postmeta.meta_value
wp_posts.post_content
wp_posts.guid
But there might be more places where the domain has been inserted.
I know that I can get the fully qualified domain name by using the windows NT network domain. I'd like to do the reverse:
Ex: User.Identity.Name = "slaterock\fflintstone";
Active Directory returns fully qualified domain name of slaterock.bedrock.us.com.
I would like to be able to get the domain portion of User.Identity.Name by querying Active Directory (LDAP) by that user. I would be using the user's email address:
(&(objectClass=user)(objectCategory=Person)(mail=fred.flintstone#slaterock.com))
I have no trouble returning the AD attributes, but I cannot figure out an absolute link between the attributes I have and the domain name returned in User.Identity.Name. I see parts of it in the domain components (DC=slaterock,DC=bedrock,DC=US,DC=blah,blah) but I need the direct link.
Thanks
First, a bit of terminology to be clear (and to help any searches you do):
the 'slaterock' in 'slaterock\fflintstone' is the NetBIOS Domain Name for the domain.
'DC=slaterock,DC=bedrock,DC=US,DC=blah,blah' is the defaultNamingContext for the domain.
CN=fred flinstone,OU=Quarry1,DC=slaterock,DC=bedrock,... is the user account's distinguishedName.
To translate from the user's distinguishedName to the NetBIOS Domain Name of their domain:
get the user account's distinguishedName and chop it up to get the defaultNamingContext.
Then do a search against the container: "CN=Partitions,CN=Configuration,DC=JohnLewis,DC=co,DC=uk"
for an object with an nCName value that matches the defaultNamingContext from above.
Get the nETBIOSName attribute of that object and you've got what you're after.